Peke in LITS - #749
Merged
Merged
Conversation
|
@Mishio-Rusterholz is attempting to deploy a commit to the robx's projects Team on Vercel. A member of the Team first needs to authorize it. |
Collaborator
|
Looks good to me 👍 |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Adds an X ("peke") mark to LITS borders to indicate that at most one of the two cells they divide would be shaded.
Matching the affordance already used in Yajilin and several other varieties: right-clicking directly on the border between two cells in play mode toggles a solving-aid X mark there, independent of cell shading.
inputpeke_ifborder); right-click inside a cell still unshades as before, and left-click still shades. A drag that starts on a border won't also shade/unshade the cell it ends on.decodeBorderLine/encodeBorderLineIfPresent), the same pattern used byheyawake.js/hitori.js. They are not written into the shareable URL, matching how most non-line puzzles treat this kind of scratch mark.